Skip to content

Data transfer not calling out the data store modes (Protected, Read/Write, Readonly) #39546

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
markjerz opened this issue May 16, 2025 · 0 comments
Labels
Content:WebAPI Web API docs goal: completeness (Experiment label) Issues about content missing important/relevant details. needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened.

Comments

@markjerz
Copy link

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/HTML_Drag_and_Drop_API/Drag_operations

What specific section or headline is this issue about?

Drag data

What information was incorrect, unhelpful, or incomplete?

It would be useful to mention the different "Drag data store mode"s that apply for different events in this section. Specifically, it's not clear that you can not access the data transfer values on dragenter, dragleave (etc). In the 3rd paragraph, you say:

During the drag, in an event listener for the dragenter and dragover events, you use the data types of the data being dragged to check whether a drop is allowed

It talks about using the types to determine if a drop is allowed but should also say that using the value is not possible.

What did you expect to see?

As above

Do you have any supporting links, references, or citations?

https://html.spec.whatwg.org/dev/dnd.html#dndevents

Do you have anything more you want to share?

No response

MDN metadata

Page report details
@markjerz markjerz added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label May 16, 2025
@github-actions github-actions bot added the Content:WebAPI Web API docs label May 16, 2025
@caugner caugner added the goal: completeness (Experiment label) Issues about content missing important/relevant details. label May 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content:WebAPI Web API docs goal: completeness (Experiment label) Issues about content missing important/relevant details. needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants